Fix QField Camera orientation by adding user-controlled rotation + persisted setting#7028
Fix QField Camera orientation by adding user-controlled rotation + persisted setting#7028kaustuvpokharel wants to merge 10 commits intomasterfrom
Conversation
769ce8a to
239edd6
Compare
🍎 MacOS DMG universal buildsDownload a MacOS DMG universal build of this PR for testing. 📱 Android buildsDownload an Android arm64 build of this PR for testing. Other Android architectures🪟 Windows buildsDownload a Windows build of this PR for testing. 🐧 Linux AppImage buildsDownload a Linux AppImage build of this PR for testing. |
53a8fd5 to
f8cef53
Compare
|
@kaustuvpokharel , nice one -- can you rebase? |
f8cef53 to
3b21baf
Compare
mohsenD98
left a comment
There was a problem hiding this comment.
Nice work @kaustuvpokharel 👍 , just 2 comment
mohsenD98
left a comment
There was a problem hiding this comment.
Okay just tested the APK, image capture rotation works fine for me. good job @kaustuvpokharel 👍
--
Suggestion about video capture: Hide/disable the rotation button during VideoCapture state and add a comment that video rotation is a follow-up
--
below some comments
…aving preview even after rotation to be inside the container
mohsenD98
left a comment
There was a problem hiding this comment.
Nice work addressing the feedback! @kaustuvpokharel 👍
|
Do not merge this yet, thanks. |

This PR tackles the inconsistent QtCamera photo orientation (auto-orientation / azimuth-related mismatch) by introducing a simple manual override that the user can set once and keep.
What changed
Applies the same selected rotation to the captured image file (pixels are rotated and orientation tags normalized) so that:
Why
QtCamera / platform auto-orientation is unreliable across devices, and I can understand why qt cannot come with a rigid fix for this, as there are thousands of devices with different mechanism within it and for one universal fix. Persisting a user-selected rotation is a pragmatic fallback that prevents repeated wrong-orientation captures without forcing a single hardcoded behavior.
Issue related that could (perhaps) be fixed with this: #7005 #5820 #5224
Demo:
trim.DFE5F7DA-4005-484F-9953-545DF3ACAD8E.MOV